LMD-Tools ReadMe

LMD-Tools ReadMe
(© by LMD Innovative, (http://www.lmd.de or http://www.lmdinnovative.com)

[Main]

Contents
Introduction
Helpfile and tutorials
Using different Language Resource File
Designtime Enhancements
Updating projects to LMD-Tools 2016

Introduction
Welcome to LMD-Tools! The latest release of this component suite provides more than 400 components.

First steps
If you encounter any problems during installation review the Installation notes (WIN32) or (VCL.NET). C++ user of BDS 2006 or later should read the corresponding special notes.
Check end of this document to get info about updating existing projects to LMD-Tools 2016.

Location of demos
Demo projects can be found in the \lmdrtlx, \lmdcore and \lmdtools folders in \demos below the installation directory. Please review demos.txt for more info about included demonstration projects for CBuilder and Delphi.

Support
If you require technical support or if you want to report problems review the Reporting Problems section.

Important Note for C++ Builder user
Speed up compile time by including the LMDMAX.H header file into one of your projects file.
Certain demonstration projects (especially in the LMD3\LMD Old, usually projects claim that some components like TLMDShapeLabel etc.are not installed) can't be compiled without installing the dcllmdlegacy_XX.bpl package (in trialversions they can not be compiled at all).
[Top]

Helpfile and tutorials
By default helpfiles are usually not included with standard/trial installers. If you did not already download current documentation pack, please visit LMD public download area and get the LMD-Tools Packs documentation package. If you are using any LMD Standalone or IDE-Tools packages, get the corresponding Help packages or download the LMD VCL Complete Help installer.
Tutorials/FAQs and other product resources can be found in the public LMD Wiki.
[Top]

Using different Language Resource File
Translated Resourcestrings can be found in

\Resources folder below installation directory for compiled versions and
\lib\source\strings folder for sourcecode versions

To change current language simply copy unit file of desired language to library file and recompile your application.
Feel free to send us modified resource units for other languages!
[Top]

Designtime Enhancements
Like for all LMD 2016 products the LMD Designtime Enhancements package is installed automatically (dcllmdrtl11_XX.bpl or LMD.Vcl.Design.Rtl.dll, compiled versions only). This package provides common design-time features for all LMD packages. Please check About dialog of any LMD control to enable/disable design-time features. For further info check LMD Designtime enhancements description.
[Top]

Updating existing projects to LMD-Tools 2016
Latest information about this topic an be found at LMD Wiki in the Updating existing projects document.

Compatibility components no installed by default
The compatibility package (now called dcllmdlegacy.dpk) is no longer installed by default (those controls which were located in the LMD Free and LMD 3.X tabs). Reason is to avoid that new LMD-Tools customers use outdated controls. On the other hand we moved on user request popular controls like TLMDSwitch back to the standard packages.
If you used any of these controls in your projects: All controls are still available - simply switch on the compatbility controls checkbox in installer.

If you upgrade from LMD-Tools 7 or earlier:

Unit changes
Several units were reorganized and removed from the packages. So you might encounter following problems when trying to compile an existing project:

File not found errors for certain units
Following units are no longer required in LMD-Tools:
lmdbredt.pas, lmdbtn.pas, lmdcctrl.pas, lmdcombo.pas, lmdcompo.pas, LMDComponent.pas, LMDCtrl.pas, lmdctrlA.pas, lmddbctA.pas, lmddbctr.pas, lmddlgS.pas, lmdeditb.pas, lmdeditc.pas, LMDEditM.pas, lmdextcA.pas, lmdextcS.pas, LMDGrapA.pas, lmdgroup.pas, LMDMemoC.pas, lmdmmS.pas, lmdnonvA.pas, lmdnonvS.pas, lmdnwgui.pas, lmdrctrl.pas, lmdrectutils.pas, lmdshapA.pas, LMDStdCA.pas, lmdstdcS.pas (for CBuilder user: .hpp/.cpp extension)

Solution:
If compiler complains about these files simply remove the unit from the uses clause. This is the recommended way.
Alternatively install the units from the source\deprecated (Delphi only, CBuilder user must always remove references). These units are actually empty but make compiler happy.
Unknown Identifier error (Components in forms)
New or different units are required for a control.

Solution:
Simply load the affected form and save it again. Delphi/CBuilder will automatically add required units to the uses clause. The simplest way is to press F9 (compile) until the project starts. The IDE will detect missing unit references and add them automatically.
Unknown Identifier error (types)
In "worst" case additional units must be added manually to the uses clause of an unit (e.g. when type or method was moved to another unit, which is not added by the Delphi IDE automatically).
If you get an unknown identifier, error simply check the helpfile or search the interface/source files to find out where the affected type/method is defined and add this unit to the uses clause.
For example: Many button related types are now defined in LMDButtonBase.pas unit instead of LMDGraph.pas. For example if you have changed in your code the style of a button, it is very likely that you have to add LMDButtonBase to the uses clause.

The mentioned issues deal with unit names only. Like always we tried to keep compatibility as far as possible (concerning properties and objects).

Other changes
The style for TLMDCustomButton and TLMDCustomSpeedButton (and controls using internal SpeedButtons) is now specified by the ButtonStyle property.
In addition the ubsWinXP, ubsWinXPCombo, ubsWinXPTool and ubsAutoDetect styles were removed, because CtlXP property (which is activated by default) is now supported by buttons. In most cases you need not to take care of this change, because we handle conversion automatically.
[Top]